Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b86d6412d15c51cf98b0d5f93f40d945d7f50413d4cd6c237f4a067da197a2be

Tx prefix hash: ad221f08d71b3a225501d0ef1cc49f0688f618549b86a0bdaef2ed123ad51497
Tx public key: e8f828fd73f0c8f2ad8f945577fcc0671c9bc5d62239b6e8bd5159f200aace68
Timestamp: 1746133259 Timestamp [UTC]: 2025-05-01 21:00:59 Age [y:d:h:m:s]: 01:199:02:26:10
Block: 1273690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406303 RingCT/type: yes/0
Extra: 01e8f828fd73f0c8f2ad8f945577fcc0671c9bc5d62239b6e8bd5159f200aace68021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3a803b4af1bbe946c24481dc14640aca5497aa24d4a238e6adbadd5afb9206bc 0.000600000000 1760973 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": 1273700, "vin": [ { "gen": { "height": 1273690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a803b4af1bbe946c24481dc14640aca5497aa24d4a238e6adbadd5afb9206bc" } } ], "extra": [ 1, 232, 248, 40, 253, 115, 240, 200, 242, 173, 143, 148, 85, 119, 252, 192, 103, 28, 155, 197, 214, 34, 57, 182, 232, 189, 81, 89, 242, 0, 170, 206, 104, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: