Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd22708b1a1f6e10e0620079eb3666f1069b467af0c34fe307edc4e45dabe691

Tx prefix hash: 3b837c701aa42b8765fbeca00a4aeec347d08f1be7eadec5a63bd7c30fcd73ef
Tx public key: 3263284ceea5ec4362a305e3d9b057bd84743e1664ce4e86eb259bd1d933663c
Timestamp: 1644805445 Timestamp [UCT]: 2022-02-14 02:24:05 Age [y:d:h:m:s]: 03:029:04:40:22
Block: 438136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 800817 RingCT/type: yes/0
Extra: 013263284ceea5ec4362a305e3d9b057bd84743e1664ce4e86eb259bd1d933663c021100000002c9067537000000000000000000

1 output(s) for total of 21.690714059000 dcy

stealth address amount amount idx
00: 4e82b6937ced6fa91770e4d5f10e5025d25334050f67c3eca9df86b509b5cbce 21.690714059000 849946 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": 438146, "vin": [ { "gen": { "height": 438136 } } ], "vout": [ { "amount": 21690714059, "target": { "key": "4e82b6937ced6fa91770e4d5f10e5025d25334050f67c3eca9df86b509b5cbce" } } ], "extra": [ 1, 50, 99, 40, 76, 238, 165, 236, 67, 98, 163, 5, 227, 217, 176, 87, 189, 132, 116, 62, 22, 100, 206, 78, 134, 235, 37, 155, 209, 217, 51, 102, 60, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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