Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7575f5174a47c29a17c7fa3b5211ccb1951ecf014b8cbcccffb1c4bb5d1e0906

Tx prefix hash: 3df6ce132ed76bfba01187a161f8e749cda07e3a8fbcce7fe880e399c2493931
Tx public key: 9b8934388d2453cd8961f2e25428ab2a2aae75eba6462e2a07bf2d455183efc8
Timestamp: 1754297587 Timestamp [UCT]: 2025-08-04 08:53:07 Age [y:d:h:m:s]: 00:057:10:24:41
Block: 1339981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39933 RingCT/type: yes/0
Extra: 019b8934388d2453cd8961f2e25428ab2a2aae75eba6462e2a07bf2d455183efc8021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9a247908abff11f0c6586a2feb36c34c27700a74826419c33c034068424f246 0.600000000000 1827796 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": 1339991, "vin": [ { "gen": { "height": 1339981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9a247908abff11f0c6586a2feb36c34c27700a74826419c33c034068424f246" } } ], "extra": [ 1, 155, 137, 52, 56, 141, 36, 83, 205, 137, 97, 242, 226, 84, 40, 171, 42, 42, 174, 117, 235, 166, 70, 46, 42, 7, 191, 45, 69, 81, 131, 239, 200, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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