Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97277e9f51b7004265edaa0cdfee490e8427b1058ee67245daaad846b19736ed

Tx prefix hash: b750fc8dc0dde4e2473d68e4b0e85b84629b29a50dd528d0b01838587e95e368
Tx public key: c0e8d34f835b5761a7210635c416a9a169634e6f7e61b17cc5aed766b85a70e6
Timestamp: 1702609588 Timestamp [UCT]: 2023-12-15 03:06:28 Age [y:d:h:m:s]: 01:332:05:56:34
Block: 913377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496314 RingCT/type: yes/0
Extra: 01c0e8d34f835b5761a7210635c416a9a169634e6f7e61b17cc5aed766b85a70e602110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 405c2e5d6d5c3f802ef0cbc89c019a41892c3fee2ec80ffd0285974447a4c6e4 0.600000000000 1370645 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": 913387, "vin": [ { "gen": { "height": 913377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "405c2e5d6d5c3f802ef0cbc89c019a41892c3fee2ec80ffd0285974447a4c6e4" } } ], "extra": [ 1, 192, 232, 211, 79, 131, 91, 87, 97, 167, 33, 6, 53, 196, 22, 169, 161, 105, 99, 78, 111, 126, 97, 177, 124, 197, 174, 215, 102, 184, 90, 112, 230, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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