Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0ed119296f3e393c4194f9ba21cfb60d5a999f6cd9d8167a81cfcdda286eebb

Tx prefix hash: 1d591b55efe15a216aa6b01ee97d17c7ad6ce3463dd2912da1e5bb82224c04ce
Tx public key: e73bf834440e09d72d671f199e271b1c6f1e7e8bdb336e2a5e944738484bd9c8
Timestamp: 1706935797 Timestamp [UCT]: 2024-02-03 04:49:57 Age [y:d:h:m:s]: 01:059:13:24:36
Block: 949225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303638 RingCT/type: yes/0
Extra: 01e73bf834440e09d72d671f199e271b1c6f1e7e8bdb336e2a5e944738484bd9c80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f2e7eee62b05f7062895d9c7148a9c8738a89432a9a32518b35075fdc7c7c4 0.600000000000 1407747 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": 949235, "vin": [ { "gen": { "height": 949225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f2e7eee62b05f7062895d9c7148a9c8738a89432a9a32518b35075fdc7c7c4" } } ], "extra": [ 1, 231, 59, 248, 52, 68, 14, 9, 215, 45, 103, 31, 25, 158, 39, 27, 28, 111, 30, 126, 139, 219, 51, 110, 42, 94, 148, 71, 56, 72, 75, 217, 200, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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