Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abdc4b4dfee484c731b16253ee1b43527b0119f989915ee4518a5ca34da7fae1

Tx prefix hash: ddd434e4bdb653688744c4030f82397f44e172670a73e80bbe884990ba7b0e5c
Tx public key: 5ee7ecbd904debbf3d982f54774ddffe87a7ac9698a9b383f9bf208bf5fa063e
Timestamp: 1735925765 Timestamp [UTC]: 2025-01-03 17:36:05 Age [y:d:h:m:s]: 01:319:10:39:28
Block: 1189465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492161 RingCT/type: yes/0
Extra: 015ee7ecbd904debbf3d982f54774ddffe87a7ac9698a9b383f9bf208bf5fa063e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d2308c7704a8f4e0b594788d3fbe4a1d0ad2ed3f8e76aa7007f7b081d7303bf 0.000600000000 1675974 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": 1189475, "vin": [ { "gen": { "height": 1189465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d2308c7704a8f4e0b594788d3fbe4a1d0ad2ed3f8e76aa7007f7b081d7303bf" } } ], "extra": [ 1, 94, 231, 236, 189, 144, 77, 235, 191, 61, 152, 47, 84, 119, 77, 223, 254, 135, 167, 172, 150, 152, 169, 179, 131, 249, 191, 32, 139, 245, 250, 6, 62, 2, 17, 0, 0, 0, 5, 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: