Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c35e78e71ef8998201aa6ebcfb1abef19cb3651083c890d6bcc3ff44a2e674

Tx prefix hash: 6f95bda193b7be6df4625dbf680691e450ff5058bec9201297fbfbbafe7df4ed
Tx public key: 8d087e59e2c91382c5a20279630f2fea2ba52d68e5b2bc91be6e758b805ddc76
Timestamp: 1739175807 Timestamp [UCT]: 2025-02-10 08:23:27 Age [y:d:h:m:s]: 00:351:07:42:51
Block: 1216093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248770 RingCT/type: yes/0
Extra: 018d087e59e2c91382c5a20279630f2fea2ba52d68e5b2bc91be6e758b805ddc760211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a90901372c0358e1ad3904494a8c825b89742f77e90d2b266670f00b0085bf13 0.600000000000 1702894 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": 1216103, "vin": [ { "gen": { "height": 1216093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a90901372c0358e1ad3904494a8c825b89742f77e90d2b266670f00b0085bf13" } } ], "extra": [ 1, 141, 8, 126, 89, 226, 201, 19, 130, 197, 162, 2, 121, 99, 15, 47, 234, 43, 165, 45, 104, 229, 178, 188, 145, 190, 110, 117, 139, 128, 93, 220, 118, 2, 17, 0, 0, 0, 2, 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