Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24ad63b2bbb44bec0170ed37b5d8b77a6d063042c86059811375de1ae7529381

Tx prefix hash: 296ab41ce3f4588de40bd61639387c7fd34b366f91a99968ba74b16502de9a5e
Tx public key: a2b1d9041a3995f75ff33117a3793121f3b49c603f4eef9443a79b87bb9db7d4
Timestamp: 1673495483 Timestamp [UCT]: 2023-01-12 03:51:23 Age [y:d:h:m:s]: 02:009:13:00:31
Block: 672863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528677 RingCT/type: yes/0
Extra: 01a2b1d9041a3995f75ff33117a3793121f3b49c603f4eef9443a79b87bb9db7d40211000000038b7b6602000000000000000000

1 output(s) for total of 3.618474491000 dcy

stealth address amount amount idx
00: 2f43bb81d0c153c7f09e8dd6c8a7d4af18207236efbe20068b71fadb37ead559 3.618474491000 1114432 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": 672873, "vin": [ { "gen": { "height": 672863 } } ], "vout": [ { "amount": 3618474491, "target": { "key": "2f43bb81d0c153c7f09e8dd6c8a7d4af18207236efbe20068b71fadb37ead559" } } ], "extra": [ 1, 162, 177, 217, 4, 26, 57, 149, 247, 95, 243, 49, 23, 163, 121, 49, 33, 243, 180, 156, 96, 63, 78, 239, 148, 67, 167, 155, 135, 187, 157, 183, 212, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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