Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd03a9aa2083ea57314b1b6cc741780e25069148caba08a805618f69bffd09da

Tx prefix hash: 35513ee7d1f46e7124e902d36424ad25577b8869889d2911f835f96c2600a711
Tx public key: 488815a6730b6c3734696f9b21d10d04524cd5f1cf05a1ac02976f16f186ff93
Timestamp: 1689203828 Timestamp [UTC]: 2023-07-12 23:17:08 Age [y:d:h:m:s]: 03:130:00:16:45
Block: 802513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 878964 RingCT/type: yes/0
Extra: 01488815a6730b6c3734696f9b21d10d04524cd5f1cf05a1ac02976f16f186ff93021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.001345678824 xmr

stealth address amount amount idx tag
00: b58e1c60c8e0359d5ab1e9491bdbb67e723820e8e89c47194d1536cf7a528b4c 0.001345678824 1253636 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": 802523, "vin": [ { "gen": { "height": 802513 } } ], "vout": [ { "amount": 1345678824, "target": { "key": "b58e1c60c8e0359d5ab1e9491bdbb67e723820e8e89c47194d1536cf7a528b4c" } } ], "extra": [ 1, 72, 136, 21, 166, 115, 11, 108, 55, 52, 105, 111, 155, 33, 209, 13, 4, 82, 76, 213, 241, 207, 5, 161, 172, 2, 151, 111, 22, 241, 134, 255, 147, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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) | monero version: