Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0af04f2cbfb147fb434dde132d677d2d8e12053deab2869b76d5a05c58941a

Tx prefix hash: 016d1b3c90de7cb681e05e086a1518a881ef5815021bd19a56a7c48cd0ae1ed3
Tx public key: a378dde4f4f3968e32661e36e74676970c55b53b4f3aa1675e91fc7cba62d135
Timestamp: 1729844349 Timestamp [UCT]: 2024-10-25 08:19:09 Age [y:d:h:m:s]: 01:020:00:31:21
Block: 1139129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272710 RingCT/type: yes/0
Extra: 01a378dde4f4f3968e32661e36e74676970c55b53b4f3aa1675e91fc7cba62d1350211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9a067622c8fd8cc68a6d8203d32ef4a7847e92d7c56124207e84eebe424735c 0.600000000000 1622894 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": 1139139, "vin": [ { "gen": { "height": 1139129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9a067622c8fd8cc68a6d8203d32ef4a7847e92d7c56124207e84eebe424735c" } } ], "extra": [ 1, 163, 120, 221, 228, 244, 243, 150, 142, 50, 102, 30, 54, 231, 70, 118, 151, 12, 85, 181, 59, 79, 58, 161, 103, 94, 145, 252, 124, 186, 98, 209, 53, 2, 17, 0, 0, 0, 4, 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