Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb6d8a3d959cf1a1f527c6189f27b42aa040af8b0951406cf1f2dab4b1b9d4a

Tx prefix hash: bd509ef02488ee3ff2c1aadb0b09264728c6ff4f0003457efdf37e528910b597
Tx public key: 9816b0db116875fb94a4a73fefbc04d05508369d2bbf63797664bcf09ce9fe89
Timestamp: 1744993371 Timestamp [UTC]: 2025-04-18 16:22:51 Age [y:d:h:m:s]: 01:026:14:01:16
Block: 1264258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269912 RingCT/type: yes/0
Extra: 019816b0db116875fb94a4a73fefbc04d05508369d2bbf63797664bcf09ce9fe89021100000008dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1388d9ef6b3b8b98267905282c1862bdcab8a4ccbcfa4e166dbc7092e5e1ca93 0.000600000000 1751453 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": 1264268, "vin": [ { "gen": { "height": 1264258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1388d9ef6b3b8b98267905282c1862bdcab8a4ccbcfa4e166dbc7092e5e1ca93" } } ], "extra": [ 1, 152, 22, 176, 219, 17, 104, 117, 251, 148, 164, 167, 63, 239, 188, 4, 208, 85, 8, 54, 157, 43, 191, 99, 121, 118, 100, 188, 240, 156, 233, 254, 137, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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: