Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ee73604fc644803e0a7c0b8efe1f23f28676a18175961fb12167c80d1a8849e

Tx prefix hash: 0c587660d721024af84831c35032ea49f3ada1966a672d4c3b5402daac5783e8
Tx public key: 52e1bfc29139f94882b58afd85d9f538bd9ec5f8643abb4d4d0dd47f6436b981
Timestamp: 1700540313 Timestamp [UCT]: 2023-11-21 04:18:33 Age [y:d:h:m:s]: 01:039:08:12:18
Block: 896224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289498 RingCT/type: yes/0
Extra: 0152e1bfc29139f94882b58afd85d9f538bd9ec5f8643abb4d4d0dd47f6436b98102110000000475e3f0e9000000000000000000

1 output(s) for total of 0.658321193000 dcy

stealth address amount amount idx
00: cc761ba192577d57f64da5fcc5fa28b77456acd2fcf1522dd9a0e1e96ce3c3bd 0.658321193000 1352499 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 dinasty-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": 896234, "vin": [ { "gen": { "height": 896224 } } ], "vout": [ { "amount": 658321193, "target": { "key": "cc761ba192577d57f64da5fcc5fa28b77456acd2fcf1522dd9a0e1e96ce3c3bd" } } ], "extra": [ 1, 82, 225, 191, 194, 145, 57, 249, 72, 130, 181, 138, 253, 133, 217, 245, 56, 189, 158, 197, 248, 100, 58, 187, 77, 77, 13, 212, 127, 100, 54, 185, 129, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8