Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0db2ed8ded3856ec20d5cb8fab5d6b283e1038668bcfa9cff612eefb3c53f1

Tx prefix hash: 8b3e6394e1e21e968bd961ae01e79064633fbabf2906a515b0fe2f01da7df5a5
Tx public key: 0b60a7abe90f72ca03a4c98ed724d9843f3c6d5f56ebff5a01dfeab2e6344182
Timestamp: 1734499868 Timestamp [UCT]: 2024-12-18 05:31:08 Age [y:d:h:m:s]: 00:104:04:51:23
Block: 1177684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74225 RingCT/type: yes/0
Extra: 010b60a7abe90f72ca03a4c98ed724d9843f3c6d5f56ebff5a01dfeab2e6344182021100000004007f978a000000000000000000

1 output(s) for total of 0.600030000000 dcy

stealth address amount amount idx
00: 428668e5d66042c6ca1d2cf31189040ec80b3943fdc9d184d9475843984c1fa0 0.600030000000 1664057 of 0

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": 1177694, "vin": [ { "gen": { "height": 1177684 } } ], "vout": [ { "amount": 600030000, "target": { "key": "428668e5d66042c6ca1d2cf31189040ec80b3943fdc9d184d9475843984c1fa0" } } ], "extra": [ 1, 11, 96, 167, 171, 233, 15, 114, 202, 3, 164, 201, 142, 215, 36, 217, 132, 63, 60, 109, 95, 86, 235, 255, 90, 1, 223, 234, 178, 230, 52, 65, 130, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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