Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e6e791d1e95ea66f21c34c3a52151e8b4dabe4306e32b880f89c58681445274

Tx prefix hash: bc9ede5dfdc583ee523fcccefbf5261507557c24ddad4c0197f65910de560a10
Tx public key: 1ac701b743c5ae75214ca339f80664b8384c09ed4e86d62758411711633db37c
Timestamp: 1770839188 Timestamp [UTC]: 2026-02-11 19:46:28 Age [y:d:h:m:s]: 00:005:00:16:33
Block: 1475717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 3551 RingCT/type: yes/0
Extra: 011ac701b743c5ae75214ca339f80664b8384c09ed4e86d62758411711633db37c020868173ea76d723d7d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc790a4ce280fd9e3bcba04bf0d9bf0218515a7fb792a9e061e23e37f56e0e3e 0.000600000000 1965021 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": 1475727, "vin": [ { "gen": { "height": 1475717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc790a4ce280fd9e3bcba04bf0d9bf0218515a7fb792a9e061e23e37f56e0e3e" } } ], "extra": [ 1, 26, 199, 1, 183, 67, 197, 174, 117, 33, 76, 163, 57, 248, 6, 100, 184, 56, 76, 9, 237, 78, 134, 214, 39, 88, 65, 23, 17, 99, 61, 179, 124, 2, 8, 104, 23, 62, 167, 109, 114, 61, 125 ], "rct_signatures": { "type": 0 } }


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