Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef9e4b3a3a272c8bce245eca672187291a2fe9de113b81bff28d5b6fc8ed23d4

Tx prefix hash: b812227bb0577c37cb6985858cfd77484820ce7a8ee1248c51432d41587309ea
Tx public key: 420746784fbc8bccb79a69d6908b07e230f2208bf56233688cbaa16157b8d435
Timestamp: 1748202733 Timestamp [UTC]: 2025-05-25 19:52:13 Age [y:d:h:m:s]: 01:180:10:27:45
Block: 1290833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392661 RingCT/type: yes/0
Extra: 01420746784fbc8bccb79a69d6908b07e230f2208bf56233688cbaa16157b8d4350211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: eff7fd858c4a4056f1fe69b0e21e5670c7cb0b90c854390c7a524498d5eee23f 0.000600000000 1778304 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": 1290843, "vin": [ { "gen": { "height": 1290833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eff7fd858c4a4056f1fe69b0e21e5670c7cb0b90c854390c7a524498d5eee23f" } } ], "extra": [ 1, 66, 7, 70, 120, 79, 188, 139, 204, 183, 154, 105, 214, 144, 139, 7, 226, 48, 242, 32, 139, 245, 98, 51, 104, 140, 186, 161, 97, 87, 184, 212, 53, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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: