Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21f81fa8c96b3c998d696629b904098f6f0ff1db04151bb861ef1dc26a9053ef

Tx prefix hash: accd3c6bc26e3a2444487397211fe6d8735170a8a1ca7a31a8afd442e56945e9
Tx public key: 06e90ad0230f822ba63b25f3c22aed07aed034d01b040efc70d0b5802931df96
Timestamp: 1720988382 Timestamp [UCT]: 2024-07-14 20:19:42 Age [y:d:h:m:s]: 00:264:15:53:24
Block: 1065757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189083 RingCT/type: yes/0
Extra: 0106e90ad0230f822ba63b25f3c22aed07aed034d01b040efc70d0b5802931df96021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 877be839471f3a5f1829752c097aa5cefedee592ea003f40d456210a724b2db2 0.600000000000 1536308 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": 1065767, "vin": [ { "gen": { "height": 1065757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "877be839471f3a5f1829752c097aa5cefedee592ea003f40d456210a724b2db2" } } ], "extra": [ 1, 6, 233, 10, 208, 35, 15, 130, 43, 166, 59, 37, 243, 194, 42, 237, 7, 174, 208, 52, 208, 27, 4, 14, 252, 112, 208, 181, 128, 41, 49, 223, 150, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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