Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04362ad2718a344927a2f2832c8765c4518b918ae631ac8b0fa53eb29820fd30

Tx prefix hash: 799b09540abd069035c6383c115a4cd5e15e03ccec43197ab2e3ae4ff20b7da3
Tx public key: 5fad4c50f05d61fd3b57552b9f23042f23d6dc345d7f5086a9c6819e9065b256
Timestamp: 1736215832 Timestamp [UCT]: 2025-01-07 02:10:32 Age [y:d:h:m:s]: 00:162:12:00:28
Block: 1191853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115843 RingCT/type: yes/0
Extra: 015fad4c50f05d61fd3b57552b9f23042f23d6dc345d7f5086a9c6819e9065b256021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e17db7a32b188c4dc7d091ac2ad19126ec665900e3b7137b44129308525afd6 0.600000000000 1678396 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": 1191863, "vin": [ { "gen": { "height": 1191853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e17db7a32b188c4dc7d091ac2ad19126ec665900e3b7137b44129308525afd6" } } ], "extra": [ 1, 95, 173, 76, 80, 240, 93, 97, 253, 59, 87, 85, 43, 159, 35, 4, 47, 35, 214, 220, 52, 93, 127, 80, 134, 169, 198, 129, 158, 144, 101, 178, 86, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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