Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652edcc01952f0fe13f7ff7385920bb28c71f132fcfe7ceb62ce902b98bfd055

Tx prefix hash: 2ee139c36fd364b953e3c45df4548993b9b3065de8e5837cfeac81756ec6b650
Tx public key: 82060d8d270f04fcc8f2f0bf6668f7dba8023e3e4db35d35e3f55ca9ccf049c8
Timestamp: 1723822337 Timestamp [UCT]: 2024-08-16 15:32:17 Age [y:d:h:m:s]: 00:302:15:24:34
Block: 1089248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216118 RingCT/type: yes/0
Extra: 0182060d8d270f04fcc8f2f0bf6668f7dba8023e3e4db35d35e3f55ca9ccf049c802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e43b3d69981693c56f7ba0618f70dcc10e2b3feefc7d5c2d345a67255538ed9 0.600000000000 1563867 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": 1089258, "vin": [ { "gen": { "height": 1089248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e43b3d69981693c56f7ba0618f70dcc10e2b3feefc7d5c2d345a67255538ed9" } } ], "extra": [ 1, 130, 6, 13, 141, 39, 15, 4, 252, 200, 242, 240, 191, 102, 104, 247, 219, 168, 2, 62, 62, 77, 179, 93, 53, 227, 245, 92, 169, 204, 240, 73, 200, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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