Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76a760e4ecae0de54a7611f9f2360c561fec1e23a3b79bfd83674004d84d1e8d

Tx prefix hash: aec1711b7091518add52b4310e4ac26115b6b54005a56add33f5edc8fdf2c10b
Tx public key: 1a6093146978fd4662c42f221243f5cffa97bbd47c0c9d6f0c70c55dca195ab7
Timestamp: 1772444776 Timestamp [UTC]: 2026-03-02 09:46:16 Age [y:d:h:m:s]: 00:078:00:36:24
Block: 1488979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49211 RingCT/type: yes/0
Extra: 011a6093146978fd4662c42f221243f5cffa97bbd47c0c9d6f0c70c55dca195ab702110000000de4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 71692260d4bedb59d90bb0661cdc2f2a10f818c7f106a8e311d8a167e6e5a8b2 0.000600000000 1978463 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": 1488989, "vin": [ { "gen": { "height": 1488979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71692260d4bedb59d90bb0661cdc2f2a10f818c7f106a8e311d8a167e6e5a8b2" } } ], "extra": [ 1, 26, 96, 147, 20, 105, 120, 253, 70, 98, 196, 47, 34, 18, 67, 245, 207, 250, 151, 187, 212, 124, 12, 157, 111, 12, 112, 197, 93, 202, 25, 90, 183, 2, 17, 0, 0, 0, 13, 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: