Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36a5cfef240366d3da240a54e910b9c6b04e1f275eea99c7b9d28fa121153443

Tx prefix hash: 14bc9a4af9a18cb259fe5d7a06215f314fd2852208fdcfc7769b8d82a154b42a
Tx public key: 97d640c834dc2ad308043040e5b6d1989af129ff8a2a9936aa264c3d440e75cb
Timestamp: 1730456577 Timestamp [UCT]: 2024-11-01 10:22:57 Age [y:d:h:m:s]: 00:149:00:05:14
Block: 1144153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106330 RingCT/type: yes/0
Extra: 0197d640c834dc2ad308043040e5b6d1989af129ff8a2a9936aa264c3d440e75cb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58a656880f8a4b3549b38acf58a8f210ebabac55dd252e1bd5647ce6a324fbf7 0.600000000000 1628272 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": 1144163, "vin": [ { "gen": { "height": 1144153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58a656880f8a4b3549b38acf58a8f210ebabac55dd252e1bd5647ce6a324fbf7" } } ], "extra": [ 1, 151, 214, 64, 200, 52, 220, 42, 211, 8, 4, 48, 64, 229, 182, 209, 152, 154, 241, 41, 255, 138, 42, 153, 54, 170, 38, 76, 61, 68, 14, 117, 203, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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