Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291ac32964fd67751c60f7198733dec9ab308631c654c57dc87a0105f518a643

Tx prefix hash: fd73c6f8fd30e545c5590fdf0b43f430607d41a24b809b225c5b7ca8ba368d06
Tx public key: 668f376e88bae339fdab65a5ae568217e46fad7a36b14adffd533c1dfac504d1
Timestamp: 1730735148 Timestamp [UCT]: 2024-11-04 15:45:48 Age [y:d:h:m:s]: 00:002:20:58:08
Block: 1146469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2061 RingCT/type: yes/0
Extra: 01668f376e88bae339fdab65a5ae568217e46fad7a36b14adffd533c1dfac504d10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f9decb2a0b593823bae2afb7747aa648def59ced8b736029bd056e9cf7282fa 0.600000000000 1631114 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": 1146479, "vin": [ { "gen": { "height": 1146469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f9decb2a0b593823bae2afb7747aa648def59ced8b736029bd056e9cf7282fa" } } ], "extra": [ 1, 102, 143, 55, 110, 136, 186, 227, 57, 253, 171, 101, 165, 174, 86, 130, 23, 228, 111, 173, 122, 54, 177, 74, 223, 253, 83, 60, 29, 250, 197, 4, 209, 2, 17, 0, 0, 0, 1, 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