Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a470b5313af8aee792f308687f4178f7414e7d9576d5ab7690ed2dfb582993

Tx prefix hash: 86aed717793116d0fc9caad8f24190989346c90516e1955d9c96bfb4f41a0330
Tx public key: a9cd80db06bcfe1ce5fab0f759ef3066ef61a1a3c339fed92e2f35ab2b873a91
Timestamp: 1718555160 Timestamp [UCT]: 2024-06-16 16:26:00 Age [y:d:h:m:s]: 00:277:06:49:23
Block: 1045596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198144 RingCT/type: yes/0
Extra: 01a9cd80db06bcfe1ce5fab0f759ef3066ef61a1a3c339fed92e2f35ab2b873a9102110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1c2f0d13a434bb9e54ac5df0b07ba1a059228d6b69e1b754a26ff7acceba87c 0.600000000000 1515207 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": 1045606, "vin": [ { "gen": { "height": 1045596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1c2f0d13a434bb9e54ac5df0b07ba1a059228d6b69e1b754a26ff7acceba87c" } } ], "extra": [ 1, 169, 205, 128, 219, 6, 188, 254, 28, 229, 250, 176, 247, 89, 239, 48, 102, 239, 97, 161, 163, 195, 57, 254, 217, 46, 47, 53, 171, 43, 135, 58, 145, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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