Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ca64e174603a1096252c329a3d70943c3cb5cfe029c023a7c2d9d3c46ed1e224

Tx prefix hash: 5f6edbe07bbba4ab23e20eef3db357be892e9b0408edeb93c7e536c5ee6c2815
Tx public key: 7727576ba26b99684bdbbf5e179aa48928d820e55f406084184f9c00d17c9e3e
Timestamp: 1713792650 Timestamp [UCT]: 2024-04-22 13:30:50 Age [y:d:h:m:s]: 00:343:06:19:01
Block: 1006094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245386 RingCT/type: yes/0
Extra: 017727576ba26b99684bdbbf5e179aa48928d820e55f406084184f9c00d17c9e3e02110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdbe241d7c16bc2ad7814ee9dbbe2846b1e5e95861cd97b5b829e0d9057324b0 0.600000000000 1467012 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1006104, "vin": [ { "gen": { "height": 1006094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdbe241d7c16bc2ad7814ee9dbbe2846b1e5e95861cd97b5b829e0d9057324b0" } } ], "extra": [ 1, 119, 39, 87, 107, 162, 107, 153, 104, 75, 219, 191, 94, 23, 154, 164, 137, 40, 216, 32, 229, 95, 64, 96, 132, 24, 79, 156, 0, 209, 124, 158, 62, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8