Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5bc0b18c4c614a68ae5d1c4ef9eb32744cd52026c0975e17bd871238c4b07fb

Tx prefix hash: 353d9f219c8ff201e88a33b54ea9956dbc798b0288bd0d265365d0c3286264bf
Tx public key: 73871d2cc02cac753d21417bd012785d7ed2f47e79792315122ac1e27a9a13c9
Timestamp: 1731024276 Timestamp [UCT]: 2024-11-08 00:04:36 Age [y:d:h:m:s]: 00:214:18:52:28
Block: 1148870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153379 RingCT/type: yes/0
Extra: 0173871d2cc02cac753d21417bd012785d7ed2f47e79792315122ac1e27a9a13c90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9e875ac4953e54f3c631373021961a68f72fb3d3cea7abe30e30a2660d8f8a5 0.600000000000 1633819 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": 1148880, "vin": [ { "gen": { "height": 1148870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9e875ac4953e54f3c631373021961a68f72fb3d3cea7abe30e30a2660d8f8a5" } } ], "extra": [ 1, 115, 135, 29, 44, 192, 44, 172, 117, 61, 33, 65, 123, 208, 18, 120, 93, 126, 210, 244, 126, 121, 121, 35, 21, 18, 42, 193, 226, 122, 154, 19, 201, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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