Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73b1f60c68e483df61929ee61c60a59b2f58e32311a9180076371e527e13fd91

Tx prefix hash: 176cc03070ea7c0cdb5bfad9daefdc87a0a31baa52763d222eb0762023c4ec37
Tx public key: 66f625f8832975092c6fcc793cdb8a73e624f21d8d4129f6d4a2f879a6260c58
Timestamp: 1741394136 Timestamp [UCT]: 2025-03-08 00:35:36 Age [y:d:h:m:s]: 00:210:18:20:09
Block: 1234465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148311 RingCT/type: yes/0
Extra: 0166f625f8832975092c6fcc793cdb8a73e624f21d8d4129f6d4a2f879a6260c580211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c04a7765ccbd0a1ef25cc427f9595e58bbcc41800a3e575c103642efd611f5 0.600000000000 1721392 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": 1234475, "vin": [ { "gen": { "height": 1234465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c04a7765ccbd0a1ef25cc427f9595e58bbcc41800a3e575c103642efd611f5" } } ], "extra": [ 1, 102, 246, 37, 248, 131, 41, 117, 9, 44, 111, 204, 121, 60, 219, 138, 115, 230, 36, 242, 29, 141, 65, 41, 246, 212, 162, 248, 121, 166, 38, 12, 88, 2, 17, 0, 0, 0, 3, 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