Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf89a31e93cda4adac0363cf2d83735bf73406dc370477218610b8e1bfdea3b3

Tx prefix hash: 25f304e9a101da0301de696c1af81e2e3dd0c12dab261f429c4c2990f5ea7620
Tx public key: 7f5dff268ca68ad6ebfd7dbb8b1044c82c65c17cd06cb0abc71aeb67c7dbb394
Timestamp: 1738683584 Timestamp [UCT]: 2025-02-04 15:39:44 Age [y:d:h:m:s]: 00:337:11:47:17
Block: 1212013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239045 RingCT/type: yes/0
Extra: 017f5dff268ca68ad6ebfd7dbb8b1044c82c65c17cd06cb0abc71aeb67c7dbb39402110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 868875e335d2f2f43cf57b3b3b2d18a19ca476590cb98085572de0fbc37b503d 0.600000000000 1698780 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": 1212023, "vin": [ { "gen": { "height": 1212013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "868875e335d2f2f43cf57b3b3b2d18a19ca476590cb98085572de0fbc37b503d" } } ], "extra": [ 1, 127, 93, 255, 38, 140, 166, 138, 214, 235, 253, 125, 187, 139, 16, 68, 200, 44, 101, 193, 124, 208, 108, 176, 171, 199, 26, 235, 103, 199, 219, 179, 148, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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