Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2833c14fccd1bae55d05c9f5e30e8912635d1cb57f86bbf79fe9cb261452d27

Tx prefix hash: bd2ef8241d3c224ab7bc39eec47390962a8a7e2d0ede065fc435347266dd10ec
Tx public key: 9fae6472c5627443adf5c41092f4acc56311cbdc2f36b7ccec266dd121d0311c
Timestamp: 1709787123 Timestamp [UCT]: 2024-03-07 04:52:03 Age [y:d:h:m:s]: 01:031:02:53:34
Block: 972891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283232 RingCT/type: yes/0
Extra: 019fae6472c5627443adf5c41092f4acc56311cbdc2f36b7ccec266dd121d0311c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c538f98d903c7619da43f48535ae31988d128a4f950027eff9e89750e1a4eaac 0.600000000000 1432810 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": 972901, "vin": [ { "gen": { "height": 972891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c538f98d903c7619da43f48535ae31988d128a4f950027eff9e89750e1a4eaac" } } ], "extra": [ 1, 159, 174, 100, 114, 197, 98, 116, 67, 173, 245, 196, 16, 146, 244, 172, 197, 99, 17, 203, 220, 47, 54, 183, 204, 236, 38, 109, 209, 33, 208, 49, 28, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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