Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abef4412693d70c178e98237768caa7f8dc015fba6119c17c71c469a37248217

Tx prefix hash: 04baae981e4ee18e92764e2f8c802cd9f475d1c50b750d2ab2f677964662517c
Tx public key: fba21a71cf81ea0ce153d69f24b40c02a73e54ff7cfe3f1857d318cf47387313
Timestamp: 1701474276 Timestamp [UCT]: 2023-12-01 23:44:36 Age [y:d:h:m:s]: 01:001:02:47:30
Block: 903965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262154 RingCT/type: yes/0
Extra: 01fba21a71cf81ea0ce153d69f24b40c02a73e54ff7cfe3f1857d318cf4738731302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.620567002000 dcy

stealth address amount amount idx
00: 7e4ac87716766ea12e8acd2332e0ee47d4c3de76fb548e74ac7007ec555a3f75 0.620567002000 1360664 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": 903975, "vin": [ { "gen": { "height": 903965 } } ], "vout": [ { "amount": 620567002, "target": { "key": "7e4ac87716766ea12e8acd2332e0ee47d4c3de76fb548e74ac7007ec555a3f75" } } ], "extra": [ 1, 251, 162, 26, 113, 207, 129, 234, 12, 225, 83, 214, 159, 36, 180, 12, 2, 167, 62, 84, 255, 124, 254, 63, 24, 87, 211, 24, 207, 71, 56, 115, 19, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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