Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff2eea5eb18b73c812d89e6466e58f76ba59028ed4084695da1873335b1d09b2

Tx prefix hash: 9f26d636e8acebd2d0cb5b30fc7fb5d39242cac12872e28d21ab308770315603
Tx public key: 492f9baea4e41d586631053c628f6a3147c5a81d880853cd985f246468fc3b1f
Timestamp: 1704461231 Timestamp [UCT]: 2024-01-05 13:27:11 Age [y:d:h:m:s]: 01:309:19:46:07
Block: 928711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480269 RingCT/type: yes/0
Extra: 01492f9baea4e41d586631053c628f6a3147c5a81d880853cd985f246468fc3b1f0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0afc5629a0c75bd7f45a7dc0890341a4f016c84474f66a2d0cc0caf746ee978 0.600000000000 1386571 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": 928721, "vin": [ { "gen": { "height": 928711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0afc5629a0c75bd7f45a7dc0890341a4f016c84474f66a2d0cc0caf746ee978" } } ], "extra": [ 1, 73, 47, 155, 174, 164, 228, 29, 88, 102, 49, 5, 60, 98, 143, 106, 49, 71, 197, 168, 29, 136, 8, 83, 205, 152, 95, 36, 100, 104, 252, 59, 31, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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