Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22262e884d7b78a2a94cbafaa78ce50d2e5552f7cf7979667566e9aa2c7f4cf2

Tx prefix hash: 36e8e15206c4bc4b4bc0bd18fe01731c415d656b18ef800521bdcb76841b592a
Tx public key: 31e859bd41224f2860855b6c32bfba6e4b04941140d4c174a4c1838a6a0c46d5
Timestamp: 1736865137 Timestamp [UCT]: 2025-01-14 14:32:17 Age [y:d:h:m:s]: 00:310:18:58:44
Block: 1197231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219623 RingCT/type: yes/0
Extra: 0131e859bd41224f2860855b6c32bfba6e4b04941140d4c174a4c1838a6a0c46d502110000001b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59ee53d1fb163cd736fbb2ad5fd777b40e3cb56f76bf8bec16b5d1066ec89a13 0.600000000000 1683838 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 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": 1197241, "vin": [ { "gen": { "height": 1197231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59ee53d1fb163cd736fbb2ad5fd777b40e3cb56f76bf8bec16b5d1066ec89a13" } } ], "extra": [ 1, 49, 232, 89, 189, 65, 34, 79, 40, 96, 133, 91, 108, 50, 191, 186, 110, 75, 4, 148, 17, 64, 212, 193, 116, 164, 193, 131, 138, 106, 12, 70, 213, 2, 17, 0, 0, 0, 27, 31, 10, 83, 235, 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