Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa6e5e9eafd9534e88fa7df7ec36f185fdf2c570f73441c3827641f88341625c

Tx prefix hash: 876af958930290b4f6454674bf8689c9bfe7b1f536204e8549841792368faecc
Tx public key: d60cd8fff29aab821fe8532d46a40d924d8b8f30401fdcfe229df69cbff3112a
Timestamp: 1742114358 Timestamp [UTC]: 2025-03-16 08:39:18 Age [y:d:h:m:s]: 01:251:12:38:13
Block: 1240438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443712 RingCT/type: yes/0
Extra: 01d60cd8fff29aab821fe8532d46a40d924d8b8f30401fdcfe229df69cbff3112a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a23ac64203f754d6bacb1d755f9d4256d7c31893deb24e35a71e9bd162aef856 0.000600000000 1727411 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": 1240448, "vin": [ { "gen": { "height": 1240438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a23ac64203f754d6bacb1d755f9d4256d7c31893deb24e35a71e9bd162aef856" } } ], "extra": [ 1, 214, 12, 216, 255, 242, 154, 171, 130, 31, 232, 83, 45, 70, 164, 13, 146, 77, 139, 143, 48, 64, 31, 220, 254, 34, 157, 246, 156, 191, 243, 17, 42, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: