Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f086fa4094094109eb68ec3b7be9a445cdee4a90f980af81a9f65c0830b937dc

Tx prefix hash: a0b3905b74f15d948ea3efae230751c1bce3cfd40dba433aaaec35a4687ccb6a
Tx public key: 3742747bbd8812b53d678259986c98b6e251b2b8d620c41aa743a839167dd277
Timestamp: 1707536748 Timestamp [UCT]: 2024-02-10 03:45:48 Age [y:d:h:m:s]: 01:059:14:45:53
Block: 954213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303662 RingCT/type: yes/0
Extra: 013742747bbd8812b53d678259986c98b6e251b2b8d620c41aa743a839167dd27702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85958fe048e98137c32fac5fb120024e1cb1ecd1fba3cb256daeae2890f877dd 0.600000000000 1413489 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": 954223, "vin": [ { "gen": { "height": 954213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85958fe048e98137c32fac5fb120024e1cb1ecd1fba3cb256daeae2890f877dd" } } ], "extra": [ 1, 55, 66, 116, 123, 189, 136, 18, 181, 61, 103, 130, 89, 152, 108, 152, 182, 226, 81, 178, 184, 214, 32, 196, 26, 167, 67, 168, 57, 22, 125, 210, 119, 2, 17, 0, 0, 0, 6, 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