Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7813e888e98cbb83304c056e2285a62ea1bc196e9cfe4ab722056a12dbf55191

Tx prefix hash: f08c450827ae7c2f3ce786b16a7859419d8d3f5c266088c8657a9c93b59b263e
Tx public key: f750d0c11f05b933f94ff30ef9fbb5d50f0eec15aa59e87dfb8b47e956064609
Timestamp: 1701737910 Timestamp [UCT]: 2023-12-05 00:58:30 Age [y:d:h:m:s]: 01:342:18:58:50
Block: 906142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503877 RingCT/type: yes/0
Extra: 01f750d0c11f05b933f94ff30ef9fbb5d50f0eec15aa59e87dfb8b47e95606460902110000000233af99f4000000000000000000

1 output(s) for total of 0.610344972000 dcy

stealth address amount amount idx
00: a0c0f1e572b5be75da0f28ac23d90086770315414419c0ba7e5d6ec961a17b4e 0.610344972000 1363065 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": 906152, "vin": [ { "gen": { "height": 906142 } } ], "vout": [ { "amount": 610344972, "target": { "key": "a0c0f1e572b5be75da0f28ac23d90086770315414419c0ba7e5d6ec961a17b4e" } } ], "extra": [ 1, 247, 80, 208, 193, 31, 5, 185, 51, 249, 79, 243, 14, 249, 251, 181, 213, 15, 14, 236, 21, 170, 89, 232, 125, 251, 139, 71, 233, 86, 6, 70, 9, 2, 17, 0, 0, 0, 2, 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