Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62d3a965e092de98b8c00e5e97608c1368112770b4a5bb40408607bb9083efa5

Tx prefix hash: 565df49b3f2cd73c0aa686a4f8fb884ebfcb5ebe2c3004fffd10d11939c7598a
Tx public key: 5dd273ba6bf9a28f14322714b9170c1c76c7cd4cfdd50ab7d7b36b36e338a612
Timestamp: 1761746036 Timestamp [UCT]: 2025-10-29 13:53:56 Age [y:d:h:m:s]: 00:012:07:14:00
Block: 1400552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8785 RingCT/type: yes/0
Extra: 015dd273ba6bf9a28f14322714b9170c1c76c7cd4cfdd50ab7d7b36b36e338a61202110000000725a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5d8dac957ed5cdb4f6b2ca24cd33e3fdb8256bdd81f344d08fd7577146353d4 0.600000000000 1888863 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": 1400562, "vin": [ { "gen": { "height": 1400552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5d8dac957ed5cdb4f6b2ca24cd33e3fdb8256bdd81f344d08fd7577146353d4" } } ], "extra": [ 1, 93, 210, 115, 186, 107, 249, 162, 143, 20, 50, 39, 20, 185, 23, 12, 28, 118, 199, 205, 76, 253, 213, 10, 183, 215, 179, 107, 54, 227, 56, 166, 18, 2, 17, 0, 0, 0, 7, 37, 163, 90, 15, 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