Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 369da4059d1c5e5d1be2f3b20fcfd8388569e9790a65b60373d2fe87efcc2f4c

Tx prefix hash: 5b6ec02a4c992a9f2c34817844a8dba91b7086ad02dd27970354368887863103
Tx public key: d88b4ac12684e81604fb7c03dbce1be7fc7356806233830e1b0252f3fb9a3c3f
Timestamp: 1667161551 Timestamp [UCT]: 2022-10-30 20:25:51 Age [y:d:h:m:s]: 02:180:05:40:48
Block: 620489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650495 RingCT/type: yes/0
Extra: 01d88b4ac12684e81604fb7c03dbce1be7fc7356806233830e1b0252f3fb9a3c3f02110000000174b6d784000000000000000000

1 output(s) for total of 5.395881401000 dcy

stealth address amount amount idx
00: 0b4029f0a935edc62b7d603ef380db16dfb153413c4cbc372fb308855ad9aa98 5.395881401000 1058368 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": 620499, "vin": [ { "gen": { "height": 620489 } } ], "vout": [ { "amount": 5395881401, "target": { "key": "0b4029f0a935edc62b7d603ef380db16dfb153413c4cbc372fb308855ad9aa98" } } ], "extra": [ 1, 216, 139, 74, 193, 38, 132, 232, 22, 4, 251, 124, 3, 219, 206, 27, 231, 252, 115, 86, 128, 98, 51, 131, 14, 27, 2, 82, 243, 251, 154, 60, 63, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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