Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bbcd9bee618fc3d3df8eded511fe5a7738873973fb88b033b355e35785a26b5

Tx prefix hash: 48ea4f67e3c3be15ab4dbb4af79e1de77cd0a0b77056c7333c58123c758b49ef
Tx public key: 70815f290f610e76873663866d9daf34e4387f7fb34ef46154c54d97f240db5c
Timestamp: 1751889513 Timestamp [UCT]: 2025-07-07 11:58:33 Age [y:d:h:m:s]: 00:177:15:06:39
Block: 1320607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125425 RingCT/type: yes/0
Extra: 0170815f290f610e76873663866d9daf34e4387f7fb34ef46154c54d97f240db5c021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad53d7dc60f47e83a0a2a5e99311cd34e2f6b62ec8b0133acc8af5cedf7c13a6 0.600000000000 1808306 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": 1320617, "vin": [ { "gen": { "height": 1320607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad53d7dc60f47e83a0a2a5e99311cd34e2f6b62ec8b0133acc8af5cedf7c13a6" } } ], "extra": [ 1, 112, 129, 95, 41, 15, 97, 14, 118, 135, 54, 99, 134, 109, 157, 175, 52, 228, 56, 127, 127, 179, 78, 244, 97, 84, 197, 77, 151, 242, 64, 219, 92, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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