Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc811d4e9048fe903d1e004f46f2e4ab4530666fb8302f27007c50810a4e74a

Tx prefix hash: e33eebe5795dacd08a90dd72530d15a68545e1df4888db8ea56d1f09f45c1cd0
Tx public key: 0151290b4ae653af9d4081daaf58e6b4e95c021203bdbfdf04e8e438c6a4c8a2
Timestamp: 1772377277 Timestamp [UTC]: 2026-03-01 15:01:17 Age [y:d:h:m:s]: 00:258:02:25:24
Block: 1488421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189871 RingCT/type: yes/0
Extra: 010151290b4ae653af9d4081daaf58e6b4e95c021203bdbfdf04e8e438c6a4c8a2021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ca868b59465e035dc0063a02bffa79fddbfd9508e2c44fc757b7d880dacdc7c8 0.000600000000 1977899 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": 1488431, "vin": [ { "gen": { "height": 1488421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca868b59465e035dc0063a02bffa79fddbfd9508e2c44fc757b7d880dacdc7c8" } } ], "extra": [ 1, 1, 81, 41, 11, 74, 230, 83, 175, 157, 64, 129, 218, 175, 88, 230, 180, 233, 92, 2, 18, 3, 189, 191, 223, 4, 232, 228, 56, 198, 164, 200, 162, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: