Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e53db670ebf89af513cc4265d0f2c6995dfc2f7d505608bbef5b0b6f23a185

Tx prefix hash: 5b9333b09f81dd53be39b43e2f969005f7cf1ef0e8235f5b860ff63cc8036f32
Tx public key: cf85cd1d4011b6b4b0a806000de50debf2e801587d32bf770aa200ae2951220f
Timestamp: 1753919318 Timestamp [UTC]: 2025-07-30 23:48:38 Age [y:d:h:m:s]: 00:221:20:28:25
Block: 1336975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157322 RingCT/type: yes/0
Extra: 01cf85cd1d4011b6b4b0a806000de50debf2e801587d32bf770aa200ae2951220f02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 44b2a958c3123b9df3701a83290c8782db7a9680c96de065d15aa115366fad2f 0.000600000000 1824778 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": 1336985, "vin": [ { "gen": { "height": 1336975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44b2a958c3123b9df3701a83290c8782db7a9680c96de065d15aa115366fad2f" } } ], "extra": [ 1, 207, 133, 205, 29, 64, 17, 182, 180, 176, 168, 6, 0, 13, 229, 13, 235, 242, 232, 1, 88, 125, 50, 191, 119, 10, 162, 0, 174, 41, 81, 34, 15, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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