Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7222effdd59f1039c80cb39214d2d32486b1671f45d819dd2f5886f20f0ed1d0

Tx prefix hash: 266f63fb4591718cd4d968c4c109bd40d81b6d606b553d79386111b9908127f2
Tx public key: dcd34322fd6575559887032cb80a000b02ec1df6f4aa8c8fd2f730793ce7a724
Timestamp: 1760403112 Timestamp [UCT]: 2025-10-14 00:51:52 Age [y:d:h:m:s]: 00:086:18:49:53
Block: 1389414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62136 RingCT/type: yes/0
Extra: 01dcd34322fd6575559887032cb80a000b02ec1df6f4aa8c8fd2f730793ce7a724021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d5fda4194275db423b84c463c67f7c3c87c97994d46a99142bcf87b7dc82237 0.600000000000 1877643 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": 1389424, "vin": [ { "gen": { "height": 1389414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d5fda4194275db423b84c463c67f7c3c87c97994d46a99142bcf87b7dc82237" } } ], "extra": [ 1, 220, 211, 67, 34, 253, 101, 117, 85, 152, 135, 3, 44, 184, 10, 0, 11, 2, 236, 29, 246, 244, 170, 140, 143, 210, 247, 48, 121, 60, 231, 167, 36, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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