Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f2b076d03383a785bc0634f11aedcd50a77fc3d1d658c9a2872cf053b03c840

Tx prefix hash: 30fb2bb8a4d2188635e407ff6d22f12c5a35411bdaca1d60b624c9d40328ed5b
Tx public key: bf2bf5056753e6c491251e5ffc960eeae607eedc177d3462930061161aebe395
Timestamp: 1577562020 Timestamp [UTC]: 2019-12-28 19:40:20 Age [y:d:h:m:s]: 06:053:02:00:52
Block: 33767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1446261 RingCT/type: yes/0
Extra: 01bf2bf5056753e6c491251e5ffc960eeae607eedc177d3462930061161aebe3950211000000044ac5aa02000000000000000000

1 output(s) for total of 0.474369511475 xmr

stealth address amount amount idx tag
00: 8a2188fb5a3106cfe1b92777bf069424af58c9359d320f5d3cdc6cfe78121251 0.474369511475 56654 of 0 -

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 dinastycoin-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": 33777, "vin": [ { "gen": { "height": 33767 } } ], "vout": [ { "amount": 474369511475, "target": { "key": "8a2188fb5a3106cfe1b92777bf069424af58c9359d320f5d3cdc6cfe78121251" } } ], "extra": [ 1, 191, 43, 245, 5, 103, 83, 230, 196, 145, 37, 30, 95, 252, 150, 14, 234, 230, 7, 238, 220, 23, 125, 52, 98, 147, 0, 97, 22, 26, 235, 227, 149, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369