Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bb60a36450953e9b6b9ed80b8e66d5cccb23347491a0d739b3bf8044b9caa18

Tx prefix hash: 49321d9a10652a5d5af6b21f586686bc8931f76586ea24a32683ab81134b2569
Tx public key: 4a29e44eac95da99eaf4d292d1b94596e31f908a84a0ff63eafedf33a47c59a6
Timestamp: 1713556564 Timestamp [UCT]: 2024-04-19 19:56:04 Age [y:d:h:m:s]: 01:024:21:19:31
Block: 1004116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278771 RingCT/type: yes/0
Extra: 014a29e44eac95da99eaf4d292d1b94596e31f908a84a0ff63eafedf33a47c59a602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ca647de60477a0fdb164370ef241f228ae9bc116fcb3fd4e98cdf0658901adb 0.600000000000 1464684 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": 1004126, "vin": [ { "gen": { "height": 1004116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ca647de60477a0fdb164370ef241f228ae9bc116fcb3fd4e98cdf0658901adb" } } ], "extra": [ 1, 74, 41, 228, 78, 172, 149, 218, 153, 234, 244, 210, 146, 209, 185, 69, 150, 227, 31, 144, 138, 132, 160, 255, 99, 234, 254, 223, 51, 164, 124, 89, 166, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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