Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89caae3481605c46ce82a99483551772951e63fa32a497f54de01c94713f0218

Tx prefix hash: 8ccf72bf2a7766d6201061a8f6e149bf786e8939f4ce20f78c775ad9fa5416b0
Tx public key: e4b2d63a76e5e3dc79c75a305e7fa302ebe992d8b8744fcc0ddb4b6f430ff250
Timestamp: 1703157918 Timestamp [UCT]: 2023-12-21 11:25:18 Age [y:d:h:m:s]: 01:177:18:26:43
Block: 917923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388124 RingCT/type: yes/0
Extra: 01e4b2d63a76e5e3dc79c75a305e7fa302ebe992d8b8744fcc0ddb4b6f430ff2500211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fda250a469564e82789d8e7b0a6f4806ea0d2c3b96109aa18fe3e2536eee097c 0.600000000000 1375547 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": 917933, "vin": [ { "gen": { "height": 917923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fda250a469564e82789d8e7b0a6f4806ea0d2c3b96109aa18fe3e2536eee097c" } } ], "extra": [ 1, 228, 178, 214, 58, 118, 229, 227, 220, 121, 199, 90, 48, 94, 127, 163, 2, 235, 233, 146, 216, 184, 116, 79, 204, 13, 219, 75, 111, 67, 15, 242, 80, 2, 17, 0, 0, 0, 3, 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