Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37437386bb60e6f3b408eaebc521881eb5e2283c6b8788261ea28ed41eb98d67

Tx prefix hash: 57c9a554152348c933861aa3e80f13a827904572dd163d1fe3c5b01be5ac007b
Tx public key: a16c14de401d84bad6a72d685325ad7cc5007b5d3b05490a8ab76b866c8fb729
Timestamp: 1694875007 Timestamp [UCT]: 2023-09-16 14:36:47 Age [y:d:h:m:s]: 01:258:02:57:46
Block: 849446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445610 RingCT/type: yes/0
Extra: 01a16c14de401d84bad6a72d685325ad7cc5007b5d3b05490a8ab76b866c8fb72902110000000675e3f0e9000000000000000000

1 output(s) for total of 0.940660348000 dcy

stealth address amount amount idx
00: 4eaa2e264d21a14e8457593d1d086428a4402d915be8a067dd6a7a82187abbaa 0.940660348000 1303112 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": 849456, "vin": [ { "gen": { "height": 849446 } } ], "vout": [ { "amount": 940660348, "target": { "key": "4eaa2e264d21a14e8457593d1d086428a4402d915be8a067dd6a7a82187abbaa" } } ], "extra": [ 1, 161, 108, 20, 222, 64, 29, 132, 186, 214, 167, 45, 104, 83, 37, 173, 124, 197, 0, 123, 93, 59, 5, 73, 10, 138, 183, 107, 134, 108, 143, 183, 41, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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