Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6ca71e3786b90d9bb3a7cb55e1809b855661e6b9c4cf73158f7a3c68f64c03

Tx prefix hash: 8d88ba7e86583dd2f8c5d26d0cfcf3e34f542cbc5e1fdf3dd9be41455ec7f6a1
Tx public key: b6ec6642a4c150c25fddcee54d45b9d21ae039d4c7c098c4e9e414f848fa816b
Timestamp: 1706569121 Timestamp [UCT]: 2024-01-29 22:58:41 Age [y:d:h:m:s]: 01:139:03:23:42
Block: 946184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360464 RingCT/type: yes/0
Extra: 01b6ec6642a4c150c25fddcee54d45b9d21ae039d4c7c098c4e9e414f848fa816b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82000f07f9073a71db3c323843415c2a4a340d180c7a62036c8e1476b8cfa914 0.600000000000 1404514 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": 946194, "vin": [ { "gen": { "height": 946184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82000f07f9073a71db3c323843415c2a4a340d180c7a62036c8e1476b8cfa914" } } ], "extra": [ 1, 182, 236, 102, 66, 164, 193, 80, 194, 95, 221, 206, 229, 77, 69, 185, 210, 26, 224, 57, 212, 199, 192, 152, 196, 233, 228, 20, 248, 72, 250, 129, 107, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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