Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34eb7d968b9c5cf6fbe408cb9efc8623c37d12878e6d3839170a567284bb8148

Tx prefix hash: 8e99e2e1f6e8a6da65c96168fb4036931b94b31d74b706a52a0cffc13968a8a2
Tx public key: 9058283ad176cfe742d702b124fff5225a84aaa919c5ff4a8710071f160d5d1b
Timestamp: 1675637640 Timestamp [UCT]: 2023-02-05 22:54:00 Age [y:d:h:m:s]: 01:340:09:05:18
Block: 690651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504239 RingCT/type: yes/0
Extra: 019058283ad176cfe742d702b124fff5225a84aaa919c5ff4a8710071f160d5d1b021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.159267946000 dcy

stealth address amount amount idx
00: f25129ed4fd9a39b5c28bc18517285291a705a3b852ba34d9e74a2c667a620a8 3.159267946000 1133385 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": 690661, "vin": [ { "gen": { "height": 690651 } } ], "vout": [ { "amount": 3159267946, "target": { "key": "f25129ed4fd9a39b5c28bc18517285291a705a3b852ba34d9e74a2c667a620a8" } } ], "extra": [ 1, 144, 88, 40, 58, 209, 118, 207, 231, 66, 215, 2, 177, 36, 255, 245, 34, 90, 132, 170, 169, 25, 197, 255, 74, 135, 16, 7, 31, 22, 13, 93, 27, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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