Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d978c11cb2dbcc388ce804c571d67599e0d7dd0f00ed7e324d2a9249ed911449

Tx prefix hash: f545ce813cb0fca4472940e5c8c271219b1840f289af69be810bf8d52d64f7a9
Tx public key: 39f914f6572ce0b18f3b220a79cca1b65d11dd8f271b1aa11a30172a228bb7dd
Timestamp: 1726432119 Timestamp [UCT]: 2024-09-15 20:28:39 Age [y:d:h:m:s]: 00:181:17:00:25
Block: 1110877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129713 RingCT/type: yes/0
Extra: 0139f914f6572ce0b18f3b220a79cca1b65d11dd8f271b1aa11a30172a228bb7dd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 867454e78e21d3c2c051072f68145766810e346099948270384a53e39ff6013e 0.600000000000 1589642 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": 1110887, "vin": [ { "gen": { "height": 1110877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "867454e78e21d3c2c051072f68145766810e346099948270384a53e39ff6013e" } } ], "extra": [ 1, 57, 249, 20, 246, 87, 44, 224, 177, 143, 59, 34, 10, 121, 204, 161, 182, 93, 17, 221, 143, 39, 27, 26, 161, 26, 48, 23, 42, 34, 139, 183, 221, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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