Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da3f5438f387b1132d5c042be8066dc6f700bfd1c3114421dbc016da5e5d5561

Tx prefix hash: 22b7014cd8a55abb29691611c65da4d5059f1be3dd7a0c8a521ece3f4dd534a3
Tx public key: 6e393dc3064e7189f780ab5b691e6db112ab1a932035b3369abda3ec43618803
Timestamp: 1699142443 Timestamp [UCT]: 2023-11-05 00:00:43 Age [y:d:h:m:s]: 01:113:05:49:39
Block: 884890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341840 RingCT/type: yes/0
Extra: 016e393dc3064e7189f780ab5b691e6db112ab1a932035b3369abda3ec43618803021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.717781235000 dcy

stealth address amount amount idx
00: 1e34239a6fb21d65375dd7d1f30cc518a050318f4e81bbbb2676c7ae6efd664e 0.717781235000 1340639 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": 884900, "vin": [ { "gen": { "height": 884890 } } ], "vout": [ { "amount": 717781235, "target": { "key": "1e34239a6fb21d65375dd7d1f30cc518a050318f4e81bbbb2676c7ae6efd664e" } } ], "extra": [ 1, 110, 57, 61, 195, 6, 78, 113, 137, 247, 128, 171, 91, 105, 30, 109, 177, 18, 171, 26, 147, 32, 53, 179, 54, 154, 189, 163, 236, 67, 97, 136, 3, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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