Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d34d496133924cbd99ac3dfdf96aea9644db03112f4abb4e64d33c8126299d38

Tx prefix hash: 651fde1b3ebcdef94ebfb27a8922b7ae8ea53bc291dc225eed415138e3121000
Tx public key: 670490519a1d5aa1f79528c64ce3948cc728a5fa75e4ede578c03ab35fd037be
Timestamp: 1750709798 Timestamp [UTC]: 2025-06-23 20:16:38 Age [y:d:h:m:s]: 01:146:10:38:12
Block: 1311334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368878 RingCT/type: yes/0
Extra: 01670490519a1d5aa1f79528c64ce3948cc728a5fa75e4ede578c03ab35fd037be02110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8d781b77c91eefbad36c042927f2aa641910c8781dea904957f1c699e5626b8b 0.000600000000 1798961 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": 1311344, "vin": [ { "gen": { "height": 1311334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d781b77c91eefbad36c042927f2aa641910c8781dea904957f1c699e5626b8b" } } ], "extra": [ 1, 103, 4, 144, 81, 154, 29, 90, 161, 247, 149, 40, 198, 76, 227, 148, 140, 199, 40, 165, 250, 117, 228, 237, 229, 120, 192, 58, 179, 95, 208, 55, 190, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: