Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7578c03d0a6e319278e8ffe61801aed2cf3d885c5238b112a3eca4a73ed13d

Tx prefix hash: 22805c176544485c271a175ed9c40c3de02318ba9d0ceac28ff7c6f0174b08dc
Tx public key: de5c25b04d480af46c88101cf369f40064e7e3ff3370176bc99f682f9e32154b
Timestamp: 1767465787 Timestamp [UTC]: 2026-01-03 18:43:07 Age [y:d:h:m:s]: 00:043:10:05:36
Block: 1447938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 30880 RingCT/type: yes/0
Extra: 01de5c25b04d480af46c88101cf369f40064e7e3ff3370176bc99f682f9e32154b02090000000ff3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a11ff679818d4d3c17e223663f4f7f0a2ebf0a23b2cb1063b8f0d5cfe6e52258 0.000600000000 1936900 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": 1447948, "vin": [ { "gen": { "height": 1447938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a11ff679818d4d3c17e223663f4f7f0a2ebf0a23b2cb1063b8f0d5cfe6e52258" } } ], "extra": [ 1, 222, 92, 37, 176, 77, 72, 10, 244, 108, 136, 16, 28, 243, 105, 244, 0, 100, 231, 227, 255, 51, 112, 23, 107, 201, 159, 104, 47, 158, 50, 21, 75, 2, 9, 0, 0, 0, 15, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


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