Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bf092c7b36c2b5b106d2bd6d077ba712ddfd3718b571f5f89f9862f2efe129e

Tx prefix hash: dd2b90c294e99f5f9a1ff96391ecf025bc36c834093771aa7df8046c54b02631
Tx public key: 872cba1ab7a33035a4b2ba8efacceaa04905175f4470aeb59996c8383a5cf2c9
Timestamp: 1761584041 Timestamp [UCT]: 2025-10-27 16:54:01 Age [y:d:h:m:s]: 00:064:10:52:54
Block: 1399194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46145 RingCT/type: yes/0
Extra: 01872cba1ab7a33035a4b2ba8efacceaa04905175f4470aeb59996c8383a5cf2c90211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7324d14512717dc505d4483ded8eb3d3e9c044bdf3e8cd8abd542bb887afe148 0.600000000000 1887499 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": 1399204, "vin": [ { "gen": { "height": 1399194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7324d14512717dc505d4483ded8eb3d3e9c044bdf3e8cd8abd542bb887afe148" } } ], "extra": [ 1, 135, 44, 186, 26, 183, 163, 48, 53, 164, 178, 186, 142, 250, 204, 234, 160, 73, 5, 23, 95, 68, 112, 174, 181, 153, 150, 200, 56, 58, 92, 242, 201, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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