Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c7189eac1a7e4866c5869ddca854f52c2affaf6115f1d99a330de7fa9fbf7e6

Tx prefix hash: 0f756fba359b3209067666b08f5571e806e90b1070a429112c3c9802ccdbf65d
Tx public key: 6b110a8b15c21fafd7dbb21dd4b6c89b8c0a2da0b9ae4841f727d1622448e69b
Timestamp: 1737225343 Timestamp [UCT]: 2025-01-18 18:35:43 Age [y:d:h:m:s]: 00:350:18:51:20
Block: 1200183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248322 RingCT/type: yes/0
Extra: 016b110a8b15c21fafd7dbb21dd4b6c89b8c0a2da0b9ae4841f727d1622448e69b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e3807a3992e7f8ea993ad142047e65c5263b74439c26ad61a0a5a4eb9d5b99f 0.600000000000 1686824 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": 1200193, "vin": [ { "gen": { "height": 1200183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e3807a3992e7f8ea993ad142047e65c5263b74439c26ad61a0a5a4eb9d5b99f" } } ], "extra": [ 1, 107, 17, 10, 139, 21, 194, 31, 175, 215, 219, 178, 29, 212, 182, 200, 155, 140, 10, 45, 160, 185, 174, 72, 65, 247, 39, 209, 98, 36, 72, 230, 155, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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