Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0809f0b260f32eb8d7b10d170832fcd58226d8b5fef00ea25a911c2b51a5bbec

Tx prefix hash: e1027f17232b3da6b246f007f5c06ce1dab9a1d4d6220b3957dfc00a003f273e
Tx public key: 2383a4be7ef0c001e5414921276cf8d278247fb6216b10d3fa9777395271fd4a
Timestamp: 1682573445 Timestamp [UCT]: 2023-04-27 05:30:45 Age [y:d:h:m:s]: 01:261:03:54:34
Block: 747524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448123 RingCT/type: yes/0
Extra: 012383a4be7ef0c001e5414921276cf8d278247fb6216b10d3fa9777395271fd4a02110000000733af99f4000000000000000000

1 output(s) for total of 2.047118027000 dcy

stealth address amount amount idx
00: a93680c2c201d9a2fb37b8ec756968e4e08a7ecf052f83ec0506943e117549d4 2.047118027000 1195205 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": 747534, "vin": [ { "gen": { "height": 747524 } } ], "vout": [ { "amount": 2047118027, "target": { "key": "a93680c2c201d9a2fb37b8ec756968e4e08a7ecf052f83ec0506943e117549d4" } } ], "extra": [ 1, 35, 131, 164, 190, 126, 240, 192, 1, 229, 65, 73, 33, 39, 108, 248, 210, 120, 36, 127, 182, 33, 107, 16, 211, 250, 151, 119, 57, 82, 113, 253, 74, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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