Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be8988390296e0ee04d9c8d5b129e9a31e1cf028fc8e896c6e03bcecacc009ba

Tx prefix hash: 961f9e78c35e839609dca97bd6fb261d93815ef8ede52f2f2fc98c888d8c16ec
Tx public key: 89699596119696567bd9a57f9e07d24ffd7bbc4bbfa57b7a252118604ca8a9d6
Timestamp: 1738848048 Timestamp [UCT]: 2025-02-06 13:20:48 Age [y:d:h:m:s]: 00:330:21:11:20
Block: 1213383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234313 RingCT/type: yes/0
Extra: 0189699596119696567bd9a57f9e07d24ffd7bbc4bbfa57b7a252118604ca8a9d60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb0b6f1638390c60cedb5c5d219c9ec14a85b8cfed68e738211a65c6eda638d3 0.600000000000 1700162 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": 1213393, "vin": [ { "gen": { "height": 1213383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0b6f1638390c60cedb5c5d219c9ec14a85b8cfed68e738211a65c6eda638d3" } } ], "extra": [ 1, 137, 105, 149, 150, 17, 150, 150, 86, 123, 217, 165, 127, 158, 7, 210, 79, 253, 123, 188, 75, 191, 165, 123, 122, 37, 33, 24, 96, 76, 168, 169, 214, 2, 17, 0, 0, 0, 6, 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