Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cfaa80ef5f8f949dce41931fda9f5bda8d41aba9f238af19e6e016d332c346e

Tx prefix hash: 58fec113399e0f7de7f31b06d0e8cc04eb138cda9618b4b8e354c3a2f44634c9
Tx public key: ad6429a6e8f1826cada2412d9f0efecdb081e6713bc2e149a3e904a52073bf7c
Timestamp: 1704134191 Timestamp [UCT]: 2024-01-01 18:36:31 Age [y:d:h:m:s]: 01:095:17:48:48
Block: 926011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329533 RingCT/type: yes/0
Extra: 01ad6429a6e8f1826cada2412d9f0efecdb081e6713bc2e149a3e904a52073bf7c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12e3d8a0b856215617002d62a775d3fc73dd634b0adfbed3f0af11bcb12f932b 0.600000000000 1383781 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": 926021, "vin": [ { "gen": { "height": 926011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12e3d8a0b856215617002d62a775d3fc73dd634b0adfbed3f0af11bcb12f932b" } } ], "extra": [ 1, 173, 100, 41, 166, 232, 241, 130, 108, 173, 162, 65, 45, 159, 14, 254, 205, 176, 129, 230, 113, 59, 194, 225, 73, 163, 233, 4, 165, 32, 115, 191, 124, 2, 17, 0, 0, 0, 2, 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