Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a6aa9b6e13478065a0b64cb05e2660b17285c7fbcf66d81695e994c94056ecd

Tx prefix hash: 9a51a2368857a0e9a0206410bf2f17bdf8ee104bc278b2b0220bafb080ecd750
Tx public key: ee7957b5d5b8e09513712fdb69d7ff0329f4736d768a63f888e31aa4d8fde824
Timestamp: 1713855302 Timestamp [UCT]: 2024-04-23 06:55:02 Age [y:d:h:m:s]: 01:051:02:39:20
Block: 1006617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297436 RingCT/type: yes/0
Extra: 01ee7957b5d5b8e09513712fdb69d7ff0329f4736d768a63f888e31aa4d8fde8240211000000030011055b000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: f52a4c2915727976a87d6037bc7147bde8ee1f4556599df58ebc9138f2247230 0.615580000000 1467695 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": 1006627, "vin": [ { "gen": { "height": 1006617 } } ], "vout": [ { "amount": 615580000, "target": { "key": "f52a4c2915727976a87d6037bc7147bde8ee1f4556599df58ebc9138f2247230" } } ], "extra": [ 1, 238, 121, 87, 181, 213, 184, 224, 149, 19, 113, 47, 219, 105, 215, 255, 3, 41, 244, 115, 109, 118, 138, 99, 248, 136, 227, 26, 164, 216, 253, 232, 36, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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