Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd6da68b5e1a76fc30e4cedf60db588e8738ae575de382807b23767b3059ead9

Tx prefix hash: 93daf78661b468ef7345ac0012ec1228b7e512309e93b2cff5d889600abdb6a6
Tx public key: fb5cf34277e7d2424a8ad65d72f39ddbe467658f2bac8abdd1d93d236c42b376
Timestamp: 1747223468 Timestamp [UTC]: 2025-05-14 11:51:08 Age [y:d:h:m:s]: 01:189:22:16:32
Block: 1282722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399889 RingCT/type: yes/0
Extra: 01fb5cf34277e7d2424a8ad65d72f39ddbe467658f2bac8abdd1d93d236c42b3760211000000069f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5535427a2d58264e4a2fe4b2e70e9fb05ad4d68342e88cf41c143aba36949c7b 0.000600000000 1770133 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": 1282732, "vin": [ { "gen": { "height": 1282722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5535427a2d58264e4a2fe4b2e70e9fb05ad4d68342e88cf41c143aba36949c7b" } } ], "extra": [ 1, 251, 92, 243, 66, 119, 231, 210, 66, 74, 138, 214, 93, 114, 243, 157, 219, 228, 103, 101, 143, 43, 172, 138, 189, 209, 217, 61, 35, 108, 66, 179, 118, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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: