Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f809732c9afa26d49f27231c3b284cc91067d6388a9418368b0f7ec4e537a9d

Tx prefix hash: 397b82dd4ce2f92c763dd9484f0c460c23a02f5741f17e41f292f3e50cbac8b4
Tx public key: cec3b232810f6a6948f8a91ddf9c8a6706d58746e33ffb40ee8d50ebd1281f8a
Timestamp: 1755862465 Timestamp [UCT]: 2025-08-22 11:34:25 Age [y:d:h:m:s]: 00:089:14:42:42
Block: 1351954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63985 RingCT/type: yes/0
Extra: 01cec3b232810f6a6948f8a91ddf9c8a6706d58746e33ffb40ee8d50ebd1281f8a021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6d0ec7869c09a46826ba4cea27817e4b03da77bf2d4c55f7d0246992f866c11 0.600000000000 1839915 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": 1351964, "vin": [ { "gen": { "height": 1351954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6d0ec7869c09a46826ba4cea27817e4b03da77bf2d4c55f7d0246992f866c11" } } ], "extra": [ 1, 206, 195, 178, 50, 129, 15, 106, 105, 72, 248, 169, 29, 223, 156, 138, 103, 6, 213, 135, 70, 227, 63, 251, 64, 238, 141, 80, 235, 209, 40, 31, 138, 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