Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8126914d561c5b04c726961cdcfce38cfbc8d5e65f1051d59e6fb40cff0a98f

Tx prefix hash: b29b00dc3034ac610b36e8dd2de8f9db42060af4cf51a87021f65b8f0434a9d4
Tx public key: 83ce3c3da16d5f56ef79a91e94cc85eff040ff21ed4338c40af0f7ef1595f98a
Timestamp: 1724948356 Timestamp [UCT]: 2024-08-29 16:19:16 Age [y:d:h:m:s]: 01:062:12:57:46
Block: 1098578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303141 RingCT/type: yes/0
Extra: 0183ce3c3da16d5f56ef79a91e94cc85eff040ff21ed4338c40af0f7ef1595f98a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f098e5777c4f807e70c687755b2dbfca9c703e65414906e9b7da42baf07011f 0.600000000000 1574343 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": 1098588, "vin": [ { "gen": { "height": 1098578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f098e5777c4f807e70c687755b2dbfca9c703e65414906e9b7da42baf07011f" } } ], "extra": [ 1, 131, 206, 60, 61, 161, 109, 95, 86, 239, 121, 169, 30, 148, 204, 133, 239, 240, 64, 255, 33, 237, 67, 56, 196, 10, 240, 247, 239, 21, 149, 249, 138, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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