Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105a7da5f0d80ec41d17280747e1084139aa3aba52223234de279a17523c8d64

Tx prefix hash: 1d90a7abfd65c66f869c90a679e1b2ccc5af246a53ec352f19f48c069793a10d
Tx public key: 4b0ba2d04f31ccdd3846ef05faf3e652db3da34080b688c022d9b5f8f257d2e1
Timestamp: 1710847977 Timestamp [UCT]: 2024-03-19 11:32:57 Age [y:d:h:m:s]: 01:048:13:32:56
Block: 981705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295686 RingCT/type: yes/0
Extra: 014b0ba2d04f31ccdd3846ef05faf3e652db3da34080b688c022d9b5f8f257d2e102110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 692f2eff3b87f124c5be3d60e3241d5f38bebe627237926a41539ca0ec1d5d68 0.600000000000 1441802 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": 981715, "vin": [ { "gen": { "height": 981705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "692f2eff3b87f124c5be3d60e3241d5f38bebe627237926a41539ca0ec1d5d68" } } ], "extra": [ 1, 75, 11, 162, 208, 79, 49, 204, 221, 56, 70, 239, 5, 250, 243, 230, 82, 219, 61, 163, 64, 128, 182, 136, 192, 34, 217, 181, 248, 242, 87, 210, 225, 2, 17, 0, 0, 0, 15, 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