Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d1fc9a95bfba98269da6d05c7533474abbabfa363a77b439be9bb73c89b1997

Tx prefix hash: 730b3078ad2829e677e1bf80ebdebc0cc659eb14920638e5cc342fab21502627
Tx public key: 23eaf3f3ed5b033e3bdaf4e95ac688d8164ba2a0b3aa6874c413352858cbf9d9
Timestamp: 1625624325 Timestamp [UCT]: 2021-07-07 02:18:45 Age [y:d:h:m:s]: 03:180:18:01:58
Block: 289408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899416 RingCT/type: yes/0
Extra: 0123eaf3f3ed5b033e3bdaf4e95ac688d8164ba2a0b3aa6874c413352858cbf9d9021100000015ed79a617000000000000000000

1 output(s) for total of 67.465844091000 dcy

stealth address amount amount idx
00: 5b79d26925f75590e0d58b7d56187e1d8f12a0a625c000b14fc1ff79e0699287 67.465844091000 606124 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": 289418, "vin": [ { "gen": { "height": 289408 } } ], "vout": [ { "amount": 67465844091, "target": { "key": "5b79d26925f75590e0d58b7d56187e1d8f12a0a625c000b14fc1ff79e0699287" } } ], "extra": [ 1, 35, 234, 243, 243, 237, 91, 3, 62, 59, 218, 244, 233, 90, 198, 136, 216, 22, 75, 162, 160, 179, 170, 104, 116, 196, 19, 53, 40, 88, 203, 249, 217, 2, 17, 0, 0, 0, 21, 237, 121, 166, 23, 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