Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9894a7537b6717db027f02440c6952c4c85d47b117aa60d914e9fafb7af6cd37

Tx prefix hash: 2a3509d4e0b0a2f1ce7502ac82c0af4feccb1522c76fc6db066b7fa20cf06fe6
Tx public key: 0238879d0f1c91aefeaf966393a325ca5cde4540833fb4d3b0a5cfcc9f91e7ff
Timestamp: 1712351569 Timestamp [UCT]: 2024-04-05 21:12:49 Age [y:d:h:m:s]: 00:223:05:44:58
Block: 994116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159832 RingCT/type: yes/0
Extra: 010238879d0f1c91aefeaf966393a325ca5cde4540833fb4d3b0a5cfcc9f91e7ff02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf9a3619a54ca31d1d737c1ca54289661435340ea18143ff240e969842eae851 0.600000000000 1454516 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": 994126, "vin": [ { "gen": { "height": 994116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf9a3619a54ca31d1d737c1ca54289661435340ea18143ff240e969842eae851" } } ], "extra": [ 1, 2, 56, 135, 157, 15, 28, 145, 174, 254, 175, 150, 99, 147, 163, 37, 202, 92, 222, 69, 64, 131, 63, 180, 211, 176, 165, 207, 204, 159, 145, 231, 255, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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