Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc3a0907db7b0e2c943a618b60d58aaa60b3f40da7a62c002d838d96882a86e

Tx prefix hash: 289775f7127226997587f6c9916dedab43c41604ec48bfdedd7b46ee1992f111
Tx public key: 35d5970f16cc368fe4e2e807b1cc91146c480b14523fb25f6af26b0b7cd12753
Timestamp: 1726208040 Timestamp [UCT]: 2024-09-13 06:14:00 Age [y:d:h:m:s]: 01:052:03:49:08
Block: 1109019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295691 RingCT/type: yes/0
Extra: 0135d5970f16cc368fe4e2e807b1cc91146c480b14523fb25f6af26b0b7cd1275302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff7da9b6dd9c0683a94b503a3f623985b0890ca8ab8c1b4f5f8cb978a713d616 0.600000000000 1587124 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": 1109029, "vin": [ { "gen": { "height": 1109019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff7da9b6dd9c0683a94b503a3f623985b0890ca8ab8c1b4f5f8cb978a713d616" } } ], "extra": [ 1, 53, 213, 151, 15, 22, 204, 54, 143, 228, 226, 232, 7, 177, 204, 145, 20, 108, 72, 11, 20, 82, 63, 178, 95, 106, 242, 107, 11, 124, 209, 39, 83, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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