Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4495e530fe8a70233570ddc463e11bb539bf6ce3f4a257791d06eadc47f5a399

Tx prefix hash: ad681edc0c89bbda59b743505a20b8084f3245b8b49f2702989cceecf97f274d
Tx public key: a3ac1e65d4dfad44b48e86b2a4330062add5bb6be07c036de5c3c51dc4142810
Timestamp: 1719254369 Timestamp [UCT]: 2024-06-24 18:39:29 Age [y:d:h:m:s]: 01:138:07:33:54
Block: 1051359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357413 RingCT/type: yes/0
Extra: 01a3ac1e65d4dfad44b48e86b2a4330062add5bb6be07c036de5c3c51dc41428100211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31c0b1e59bc1dba4e8ea76ce2ea727746acba0d6414f3463136c38ccd1f47805 0.600000000000 1521670 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": 1051369, "vin": [ { "gen": { "height": 1051359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31c0b1e59bc1dba4e8ea76ce2ea727746acba0d6414f3463136c38ccd1f47805" } } ], "extra": [ 1, 163, 172, 30, 101, 212, 223, 173, 68, 180, 142, 134, 178, 164, 51, 0, 98, 173, 213, 187, 107, 224, 124, 3, 109, 229, 195, 197, 29, 196, 20, 40, 16, 2, 17, 0, 0, 0, 9, 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