Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0aedd751233b39edd40bbf6c0db297f05a404f8bf158b07c32ce4296da00c3e

Tx prefix hash: 2cbc8c908aa7eca960e13e4c4dfc73136e6853d6881b476385c3cf905b354e79
Tx public key: 07521b453bef4a03c455596c2ecf1a00b50de537a8f12138a2f63448269187ae
Timestamp: 1740830441 Timestamp [UTC]: 2025-03-01 12:00:41 Age [y:d:h:m:s]: 01:034:11:27:59
Block: 1229784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283184 RingCT/type: yes/0
Extra: 0107521b453bef4a03c455596c2ecf1a00b50de537a8f12138a2f63448269187ae021100000009007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d7ebe9edb64ddfb450aaa6a58f971f546edc6c9d9613a2038059b282bb2aa8c9 0.000600000000 1716673 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": 1229794, "vin": [ { "gen": { "height": 1229784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7ebe9edb64ddfb450aaa6a58f971f546edc6c9d9613a2038059b282bb2aa8c9" } } ], "extra": [ 1, 7, 82, 27, 69, 59, 239, 74, 3, 196, 85, 89, 108, 46, 207, 26, 0, 181, 13, 229, 55, 168, 241, 33, 56, 162, 246, 52, 72, 38, 145, 135, 174, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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) | dinastycoin version: tesla-369