Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5dec0dcd0d9c9e7d29dd067cc12e6bee844377054b322edb49cb336e4e951aa

Tx prefix hash: a7574e906cb9b53641d156e6be91ef3090f33f18b5841c0f73b2bf7457a62559
Tx public key: 8379d00adb10ddc5c9a3125b03e991a6057599139a98f0ffb9794ed50f21243b
Timestamp: 1699345047 Timestamp [UCT]: 2023-11-07 08:17:27 Age [y:d:h:m:s]: 01:175:21:08:13
Block: 886317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386899 RingCT/type: yes/0
Extra: 018379d00adb10ddc5c9a3125b03e991a6057599139a98f0ffb9794ed50f21243b021100000001faf35c9c000000000000000000

1 output(s) for total of 0.710009001000 dcy

stealth address amount amount idx
00: 0ab28490369976ff77d0da215ba22696d5ff7f63307fff174f134ce64b46e20a 0.710009001000 1342132 of 0

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": 886327, "vin": [ { "gen": { "height": 886317 } } ], "vout": [ { "amount": 710009001, "target": { "key": "0ab28490369976ff77d0da215ba22696d5ff7f63307fff174f134ce64b46e20a" } } ], "extra": [ 1, 131, 121, 208, 10, 219, 16, 221, 197, 201, 163, 18, 91, 3, 233, 145, 166, 5, 117, 153, 19, 154, 152, 240, 255, 185, 121, 78, 213, 15, 33, 36, 59, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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