Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e692e9fc3e52d951c63a1f64a87ab59cdab27510ea0d5518ed48ec3f62034aa

Tx prefix hash: ff8b499c26e009f213994184cab8405cf248f296ef01aea10de59655d212d926
Tx public key: 4b48dc4249285e33704393de9040e42d9c6f0da745317f062d4aaf1844a32ee2
Timestamp: 1705409978 Timestamp [UTC]: 2024-01-16 12:59:38 Age [y:d:h:m:s]: 02:039:19:55:49
Block: 936569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548104 RingCT/type: yes/0
Extra: 014b48dc4249285e33704393de9040e42d9c6f0da745317f062d4aaf1844a32ee202110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1c2a127eb7903817159342018de57a804d57df39baeb6cb2fbae8711600d3afa 0.000600000000 1394597 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": 936579, "vin": [ { "gen": { "height": 936569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c2a127eb7903817159342018de57a804d57df39baeb6cb2fbae8711600d3afa" } } ], "extra": [ 1, 75, 72, 220, 66, 73, 40, 94, 51, 112, 67, 147, 222, 144, 64, 228, 45, 156, 111, 13, 167, 69, 49, 127, 6, 45, 74, 175, 24, 68, 163, 46, 226, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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) | dinastycoin version: tesla-369