Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68ec808b91672f651c2031c1e55b3bee8e104f7f2c9ecb49d02acac7d45d809

Tx prefix hash: 3852081956b970727e2ef9566adcb5c9cc0ae060b394432b8759a9b01f52d74b
Tx public key: feb0fcad808dfb1d3d2a012234be31a69942b754196cb7e0888e205453dde94c
Timestamp: 1706984075 Timestamp [UCT]: 2024-02-03 18:14:35 Age [y:d:h:m:s]: 00:341:19:21:00
Block: 949631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244711 RingCT/type: yes/0
Extra: 01feb0fcad808dfb1d3d2a012234be31a69942b754196cb7e0888e205453dde94c0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ab3808b8809d0009a1670d72c4a05e05859c90c65f9c7914e75edf810889e55 0.600000000000 1408161 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": 949641, "vin": [ { "gen": { "height": 949631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ab3808b8809d0009a1670d72c4a05e05859c90c65f9c7914e75edf810889e55" } } ], "extra": [ 1, 254, 176, 252, 173, 128, 141, 251, 29, 61, 42, 1, 34, 52, 190, 49, 166, 153, 66, 183, 84, 25, 108, 183, 224, 136, 142, 32, 84, 83, 221, 233, 76, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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