Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3a61d7ec7df57f5bfdc39be3ff8866073ff65871877c27dd51804beb2812d7e

Tx prefix hash: 23cac3dc7d813f753b47e0c154fd80e81c1fe9a1c4ecef0d0bf3392c2694618c
Tx public key: 0ed96e25ed857cd59d1e35f302b8d61a6d375dd839e7c2252433a9ddbd423ebb
Timestamp: 1694987814 Timestamp [UCT]: 2023-09-17 21:56:54 Age [y:d:h:m:s]: 01:204:13:57:09
Block: 850378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407310 RingCT/type: yes/0
Extra: 010ed96e25ed857cd59d1e35f302b8d61a6d375dd839e7c2252433a9ddbd423ebb021100000007faf35c9c000000000000000000

1 output(s) for total of 0.933995392000 dcy

stealth address amount amount idx
00: a1cdfedfb86ddb41ad8485d80b37e3a92813afb2c1a79284ba5a5e7ddd73f9b7 0.933995392000 1304094 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": 850388, "vin": [ { "gen": { "height": 850378 } } ], "vout": [ { "amount": 933995392, "target": { "key": "a1cdfedfb86ddb41ad8485d80b37e3a92813afb2c1a79284ba5a5e7ddd73f9b7" } } ], "extra": [ 1, 14, 217, 110, 37, 237, 133, 124, 213, 157, 30, 53, 243, 2, 184, 214, 26, 109, 55, 93, 216, 57, 231, 194, 37, 36, 51, 169, 221, 189, 66, 62, 187, 2, 17, 0, 0, 0, 7, 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