Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc293aa6201773583b9ea0c25aea2b3c41f4133fd7de3d10e826d7a03950f89

Tx prefix hash: 80fb7073c3e0136f23dfc40a9d67cb8d5228796ab62be185da293b13e085c7e7
Tx public key: 8eb1a9978664a6645d09f3fab3e8ef92a535a407941de601e80426876a7293b3
Timestamp: 1770448823 Timestamp [UTC]: 2026-02-07 07:20:23 Age [y:d:h:m:s]: 00:009:05:10:59
Block: 1472493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 6557 RingCT/type: yes/0
Extra: 018eb1a9978664a6645d09f3fab3e8ef92a535a407941de601e80426876a7293b302081174b39b83fbffd6

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 57f2d397ccd469e8c23321ef60f126e6ef0f6b4b3d7a9b3c1af58ddd98b9ae07 0.000600000000 1961773 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 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": 1472503, "vin": [ { "gen": { "height": 1472493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57f2d397ccd469e8c23321ef60f126e6ef0f6b4b3d7a9b3c1af58ddd98b9ae07" } } ], "extra": [ 1, 142, 177, 169, 151, 134, 100, 166, 100, 93, 9, 243, 250, 179, 232, 239, 146, 165, 53, 164, 7, 148, 29, 230, 1, 232, 4, 38, 135, 106, 114, 147, 179, 2, 8, 17, 116, 179, 155, 131, 251, 255, 214 ], "rct_signatures": { "type": 0 } }


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