Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0563da0f9fb83ecfe0c080998c1f980378386eb070d38c9e9aba655fe3c11190

Tx prefix hash: 28db4eb96f3a53e8020bec01cff1b6b1644ff1bc055652a7a5abcb968be14291
Tx public key: 9e1c000aea5c90c405149dc755aa2678674465fce80988574f7b2420bb9c34f3
Timestamp: 1631499987 Timestamp [UCT]: 2021-09-13 02:26:27 Age [y:d:h:m:s]: 03:233:13:48:31
Block: 332653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 942328 RingCT/type: yes/0
Extra: 019e1c000aea5c90c405149dc755aa2678674465fce80988574f7b2420bb9c34f302110000000c36fe6557000000000000000000

1 output(s) for total of 48.504603949000 dcy

stealth address amount amount idx
00: b1e76a56af94c4713030e00f90aed4f4a48f6d8a7cb6c64fcc3dc24523282027 48.504603949000 686838 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": 332663, "vin": [ { "gen": { "height": 332653 } } ], "vout": [ { "amount": 48504603949, "target": { "key": "b1e76a56af94c4713030e00f90aed4f4a48f6d8a7cb6c64fcc3dc24523282027" } } ], "extra": [ 1, 158, 28, 0, 10, 234, 92, 144, 196, 5, 20, 157, 199, 85, 170, 38, 120, 103, 68, 101, 252, 232, 9, 136, 87, 79, 123, 36, 32, 187, 156, 52, 243, 2, 17, 0, 0, 0, 12, 54, 254, 101, 87, 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