Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c35fe1647c51f4484ce592d1f526db1d60dc9c264bc833bcd55ab50796e73a90

Tx prefix hash: 53c4dacc61569a0652d1f0513817c78a4270480fcaf167590591906b698d768b
Tx public key: 84506f0eec92b6a307af28a23e5b85fe317b1dcc5e557413c1aaff70b940a782
Timestamp: 1719946388 Timestamp [UCT]: 2024-07-02 18:53:08 Age [y:d:h:m:s]: 00:289:10:44:48
Block: 1057111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206824 RingCT/type: yes/0
Extra: 0184506f0eec92b6a307af28a23e5b85fe317b1dcc5e557413c1aaff70b940a7820211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e451414155c06cc32465a2f4c952c8cb9e227eb19cb31f4ef9a6f8536802f1bd 0.600000000000 1527540 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": 1057121, "vin": [ { "gen": { "height": 1057111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e451414155c06cc32465a2f4c952c8cb9e227eb19cb31f4ef9a6f8536802f1bd" } } ], "extra": [ 1, 132, 80, 111, 14, 236, 146, 182, 163, 7, 175, 40, 162, 62, 91, 133, 254, 49, 123, 29, 204, 94, 85, 116, 19, 193, 170, 255, 112, 185, 64, 167, 130, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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