Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5dcfbcf4e8d2e65d064986bc9e3a4a49a09dab6547095c914e570e92847987

Tx prefix hash: 5f30fd140fa7d9b0f6acbee2058251ca1aa4de25a58f26505a7a07a92da6ff1d
Tx public key: ac0f6cc798c9bd6f1269462464fd80f149b3855bfb7ac6b5ff1fe24cf0978afd
Timestamp: 1752599058 Timestamp [UTC]: 2025-07-15 17:04:18 Age [y:d:h:m:s]: 01:121:17:19:30
Block: 1326141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351931 RingCT/type: yes/0
Extra: 01ac0f6cc798c9bd6f1269462464fd80f149b3855bfb7ac6b5ff1fe24cf0978afd021100000002d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1c14a4c372c620ca5b48b0cad7fb57ae5f6bc8b2b6af5e3763003b4d93bef993 0.000600000000 1813890 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": 1326151, "vin": [ { "gen": { "height": 1326141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c14a4c372c620ca5b48b0cad7fb57ae5f6bc8b2b6af5e3763003b4d93bef993" } } ], "extra": [ 1, 172, 15, 108, 199, 152, 201, 189, 111, 18, 105, 70, 36, 100, 253, 128, 241, 73, 179, 133, 91, 251, 122, 198, 181, 255, 31, 226, 76, 240, 151, 138, 253, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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: