Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10dd69b98017017c80c9e438586f9902639876479c0431228868b0ce1375a241

Tx prefix hash: 0207ba2a74efb0f2d7dd76902a1685f065d3589569c00ef4001a6f770a8342d3
Tx public key: c3bdddfe821dc63aa8dc1d4eaa713346fce7343201ea6a04024d60bb3dc3b66d
Timestamp: 1576037385 Timestamp [UTC]: 2019-12-11 04:09:45 Age [y:d:h:m:s]: 06:056:10:13:42
Block: 25126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1444692 RingCT/type: yes/0
Extra: 01c3bdddfe821dc63aa8dc1d4eaa713346fce7343201ea6a04024d60bb3dc3b66d021100000004ad433a0b000000000000000000

1 output(s) for total of 0.506696612833 xmr

stealth address amount amount idx tag
00: 490c1b957802648e43027d4f6c2f42f02aa6f11756bb3f01bc53f960deaa2a0e 0.506696612833 41391 of 0 -

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": 25136, "vin": [ { "gen": { "height": 25126 } } ], "vout": [ { "amount": 506696612833, "target": { "key": "490c1b957802648e43027d4f6c2f42f02aa6f11756bb3f01bc53f960deaa2a0e" } } ], "extra": [ 1, 195, 189, 221, 254, 130, 29, 198, 58, 168, 220, 29, 78, 170, 113, 51, 70, 252, 231, 52, 50, 1, 234, 106, 4, 2, 77, 96, 187, 61, 195, 182, 109, 2, 17, 0, 0, 0, 4, 173, 67, 58, 11, 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