Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5060a159ed7315a41adcfb3ab670467f533a044c49e4ca05b7ea8d4e72fe97

Tx prefix hash: b2c748c2edbf9cd40908b11ec54e0fa7e4e03205745ac453aae67fa738ed47f1
Tx public key: 9e8222c9962bcd5fcc8a652ff6fb91a76606d8aed96a8c6eb1e2a3f047d4a1bf
Timestamp: 1760689250 Timestamp [UTC]: 2025-10-17 08:20:50 Age [y:d:h:m:s]: 01:030:15:57:39
Block: 1391775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288240 RingCT/type: yes/0
Extra: 019e8222c9962bcd5fcc8a652ff6fb91a76606d8aed96a8c6eb1e2a3f047d4a1bf0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd388658402a865c5eaaef7344f1f5f0b7fc09cdacd455ee69f35fcc6c263789 0.000600000000 1880022 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": 1391785, "vin": [ { "gen": { "height": 1391775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd388658402a865c5eaaef7344f1f5f0b7fc09cdacd455ee69f35fcc6c263789" } } ], "extra": [ 1, 158, 130, 34, 201, 150, 43, 205, 95, 204, 138, 101, 47, 246, 251, 145, 167, 102, 6, 216, 174, 217, 106, 140, 110, 177, 226, 163, 240, 71, 212, 161, 191, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: