Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3398b4e1e8c0bc62d3fca1e318bea500cbe847236e61633351214d0e40a865

Tx prefix hash: bb76a977013d1c62b08197808d3c171c4997ab0ff8bec10d32ea1a1601ac01fd
Tx public key: ffe9133ac6714e15e1c5b6e3dffdfd57b68227ae888815ca4bbb8c8f2afacc0c
Timestamp: 1772773868 Timestamp [UTC]: 2026-03-06 05:11:08 Age [y:d:h:m:s]: 00:259:23:30:39
Block: 1491713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191459 RingCT/type: yes/0
Extra: 01ffe9133ac6714e15e1c5b6e3dffdfd57b68227ae888815ca4bbb8c8f2afacc0c021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a32aeca4668ad303ca8d372811ef0000183dc6203db7393dd9b4ca82409019c 0.000600000000 1981233 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": 1491723, "vin": [ { "gen": { "height": 1491713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a32aeca4668ad303ca8d372811ef0000183dc6203db7393dd9b4ca82409019c" } } ], "extra": [ 1, 255, 233, 19, 58, 198, 113, 78, 21, 225, 197, 182, 227, 223, 253, 253, 87, 182, 130, 39, 174, 136, 136, 21, 202, 75, 187, 140, 143, 42, 250, 204, 12, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: