Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5914ca7fc91d103dd16d96199e03819c301aa2f6dc24d726f19871c03684378

Tx prefix hash: 99d50c0c35c84521b9b7bc51c462d07d352a50811c6a741ac014b7603c661564
Tx public key: e5811b912e0feed953de5f0343c4b838727c5e0a4b41d11c71d067f4eeabf0a8
Timestamp: 1711768728 Timestamp [UCT]: 2024-03-30 03:18:48 Age [y:d:h:m:s]: 00:300:19:43:27
Block: 989335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215259 RingCT/type: yes/0
Extra: 01e5811b912e0feed953de5f0343c4b838727c5e0a4b41d11c71d067f4eeabf0a80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06f80b90ae57975af6e7450574168bd14f09f3729542694786635c097115e1fe 0.600000000000 1449632 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": 989345, "vin": [ { "gen": { "height": 989335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06f80b90ae57975af6e7450574168bd14f09f3729542694786635c097115e1fe" } } ], "extra": [ 1, 229, 129, 27, 145, 46, 15, 238, 217, 83, 222, 95, 3, 67, 196, 184, 56, 114, 124, 94, 10, 75, 65, 209, 28, 113, 208, 103, 244, 238, 171, 240, 168, 2, 17, 0, 0, 0, 1, 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