Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdb0e52f744c34c442fd4fe5d069217bb21aba9da8a609d6547965243616b9f2

Tx prefix hash: 06544274f6b7578b5633d95e8dfbfc01a1a4a559374856492dae42a543d2a6e4
Tx public key: aa159f885a46949f4788b84634ce2f19d817e7b0ee4c5e0a85e6b01ec9b0f0cd
Timestamp: 1580366278 Timestamp [UTC]: 2020-01-30 06:37:58 Age [y:d:h:m:s]: 06:295:06:00:39
Block: 54937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1626948 RingCT/type: yes/0
Extra: 01aa159f885a46949f4788b84634ce2f19d817e7b0ee4c5e0a85e6b01ec9b0f0cd0211000000054943cd9f000000000000000000

1 output(s) for total of 0.403619127554 xmr

stealth address amount amount idx tag
00: 76796f986f1e75592499440d829ffb0b4bf482308bc524c130d14086d6407b50 0.403619127554 101599 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": 54947, "vin": [ { "gen": { "height": 54937 } } ], "vout": [ { "amount": 403619127554, "target": { "key": "76796f986f1e75592499440d829ffb0b4bf482308bc524c130d14086d6407b50" } } ], "extra": [ 1, 170, 21, 159, 136, 90, 70, 148, 159, 71, 136, 184, 70, 52, 206, 47, 25, 216, 23, 231, 176, 238, 76, 94, 10, 133, 230, 176, 30, 201, 176, 240, 205, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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: